home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / u_man / cat3 / Tk / geomreq.z / geomreq
Encoding:
Text File  |  1998-10-30  |  5.5 KB  |  133 lines
  1.  
  2.  
  3.  
  4. TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt((((3333TTTTkkkk))))                                TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt((((3333TTTTkkkk))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      Tk_GeometryRequest, Tk_SetInternalBorder - specify desired geometry or
  10.      internal border for a window
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      ####iiiinnnncccclllluuuuddddeeee <<<<ttttkkkk....hhhh>>>>
  14.  
  15.      TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt(_t_k_w_i_n, _r_e_q_W_i_d_t_h, _r_e_q_H_e_i_g_h_t)
  16.  
  17.      TTTTkkkk____SSSSeeeettttIIIInnnntttteeeerrrrnnnnaaaallllBBBBoooorrrrddddeeeerrrr(_t_k_w_i_n, _w_i_d_t_h)
  18.  
  19. AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS
  20.      Tk_Window    _t_k_w_i_n        (in)      Window for which geometry is being
  21.                                          requested.
  22.  
  23.      int          _r_e_q_W_i_d_t_h     (in)      Desired width for _t_k_w_i_n, in pixel
  24.                                          units.
  25.  
  26.      int          _r_e_q_H_e_i_g_h_t    (in)      Desired height for _t_k_w_i_n, in pixel
  27.                                          units.
  28.  
  29.      int          _w_i_d_t_h        (in)      Space to leave for internal border
  30.                                          for _t_k_w_i_n, in pixel units.
  31.  
  32.  
  33. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  34.      TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt is called by widget code to indicate its preference
  35.      for the dimensions of a particular window.  The arguments to
  36.      TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt are made available to the geometry manager for the
  37.      window, which then decides on the actual geometry for the window.
  38.      Although geometry managers generally try to satisfy requests made to
  39.      TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt, there is no guarantee that this will always be
  40.      possible.  Widget code should not assume that a geometry request will be
  41.      satisfied until it receives a CCCCoooonnnnffffiiiigggguuuurrrreeeeNNNNoooottttiiiiffffyyyy event indicating that the
  42.      geometry change has occurred.  Widget code should never call procedures
  43.      like TTTTkkkk____RRRReeeessssiiiizzzzeeeeWWWWiiiinnnnddddoooowwww directly.  Instead, it should invoke
  44.      TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt and leave the final geometry decisions to the geometry
  45.      manager.
  46.  
  47.      If _t_k_w_i_n is a top-level window, then the geometry information will be
  48.      passed to the window manager using the standard ICCCM protocol.
  49.  
  50.      TTTTkkkk____SSSSeeeettttIIIInnnntttteeeerrrrnnnnaaaallllBBBBoooorrrrddddeeeerrrr is called by widget code to indicate that the widget
  51.      has an internal border.  This means that the widget draws a decorative
  52.      border inside the window instead of using the standard X borders, which
  53.      are external to the window's area.  For example, internal borders are
  54.      used to draw 3-D effects.  _W_i_d_t_h specifies the width of the border in
  55.      pixels.  Geometry managers will use this information to avoid placing any
  56.      children of _t_k_w_i_n overlapping the outermost _w_i_d_t_h pixels of _t_k_w_i_n's area.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt((((3333TTTTkkkk))))                                TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt((((3333TTTTkkkk))))
  71.  
  72.  
  73.  
  74.      The information specified in calls to TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt and
  75.      TTTTkkkk____SSSSeeeettttIIIInnnntttteeeerrrrnnnnaaaallllBBBBoooorrrrddddeeeerrrr can be retrieved using the macros TTTTkkkk____RRRReeeeqqqqWWWWiiiiddddtttthhhh,
  76.      TTTTkkkk____RRRReeeeqqqqHHHHeeeeiiiigggghhhhtttt, and TTTTkkkk____IIIInnnntttteeeerrrrnnnnaaaallllBBBBoooorrrrddddeeeerrrrWWWWiiiiddddtttthhhh.  See the TTTTkkkk____WWWWiiiinnnnddddoooowwwwIIIIdddd manual
  77.      entry for details.
  78.  
  79.  
  80. KKKKEEEEYYYYWWWWOOOORRRRDDDDSSSS
  81.      geometry, request
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.